Fix invalid gh-aw workflow lock output#22
Draft
Copilot wants to merge 2 commits into
Draft
Conversation
Co-authored-by: mrjf <180956+mrjf@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix Evergreen workflow failure due to invalid concurrency key
Fix invalid gh-aw workflow lock output
May 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Evergreen was failing at workflow startup because gh-aw v0.74.4 emitted GitHub Actions YAML with invalid
concurrency.queueand unsupported permission scopes. Autoloop had the same invalid concurrency output and would fail on its next run.Workflow lockfile cleanup
queue: maxentries from Evergreen and Autoloop lockfiles.copilot-requestsvulnerability-alertsgh-aw setup pin
.github/aw/actions-lock.jsonto match the v0.74.3 pin.